To be used in a future for more zk-friendly merkjlization hash functions.

SHA256 is very computational-intense to be implemented in zk-STARK, which will very significantly increase the size of proofs and the time required to generate them. Thus, use of zk-START-friendly hash function is advised.

Thus, a multi-protocol commitment must support different hash functions, and commit to the specific use function value alongside such parameters as entropy and the depth of the tree.

It can be that information about the used hash function should be optional, since it can be deduces from the single-use seal type, which commits to the closing method; and each closing method can be used with just one type of MPC (and its hash function). But anyway, this may significantly simplify validation logic, so consider adding info about the hash to the MPC itself (or use some feature flags to indicate that).